-
Notifications
You must be signed in to change notification settings - Fork 15
fix: getPDPService always returns a pdpOffering #324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Deploying with
|
Status | Name | Latest Commit | Preview URL | Updated (UTC) |
---|---|---|---|---|
✅ Deployment successful! View logs |
synapse-dev | 7f8e8c3 | Commit Preview URL Branch Preview URL |
Oct 17 2025, 09:25 PM |
Astro build errors look unrelated:
|
It works locally. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
astro error is because current
Node.js became v25.0.0, so we have a new incompatibility to look at, not relevant here
Reviewer @rvagg
See also FilOzone/filecoin-services#295
Neither of these issues were caught before because we currently catch all exceptions in SPRegistryService.getPDPService, a bad policy.
I don't remove the catch-all because there are more problems after this; for example,
'should select a random provider when no providerId specified'
will fail when trying to create the data set.Changes